System, method and computer program product for managing access to systems, products, and data based on information associated with a physical location of a user

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for managing access to data based on information associated with a physical location of a user. These mechanisms and methods for managing access to systems, products, or data based on information associated with a physical location of a user can enable improved data management efficiency, enhanced data management accuracy, decreased data management costs, decreased licensing costs, increased security, additional marketing opportunities, etc.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional Patent Application No. 61/807,954, entitled “SYSTEM AND METHOD FOR LOCATION AND PROXIMITY BASED LICENSING,” by Daniel Thomas Harrison, filed Apr. 3, 2013 (Attorney Docket No. 1163PROV), the entire contents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

One or more implementations relate generally to managing data access, and more particularly to managing data access based on identified information.

BACKGROUND

The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.

Licensing is a common form of controlling access to data. For example, product developers may utilize a license to control the usage of their product or access to information. Unfortunately, techniques for implementing effective licenses have been associated with various limitations. Just by way of example, current licenses do not take into consideration a multitude of environmental factors that may have an impact on the licenses. Accordingly, it is desirable to provide techniques for managing access to data based on information associated with a physical location of a user.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms and methods for managing access to data based on information associated with a physical location of a user. These mechanisms and methods for managing access to systems, products, and data based on information associated with a physical location of a user can enable improved data management efficiency, enhanced data management accuracy, decreased data management costs, decreased licensing costs, increased security, additional marketing opportunities, etc.

In an embodiment and by way of example, a method for managing access to systems, products, and data based on information associated with a physical location of a user is provided. In one embodiment, information associated with a physical location of a user is identified. Additionally, access to one or more of systems, products, and data is managed, based on the identified information.

While one or more implementations and techniques are described with reference to an embodiment in which managing access to systems, products, and data based on information associated with a physical location of a user is implemented in a system having an application server providing a front end for an on-demand database system capable of supporting multiple tenants, the one or more implementations and techniques are not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with one another in any combination. The one or more implementations encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments do not necessarily address any of these deficiencies. In other words, different embodiments may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples, the one or more implementations are not limited to the examples depicted in the figures.

FIG. 1 illustrates a method for managing access to systems, products, and data based on information associated with a physical location of a user, in accordance with one embodiment;

FIG. 2 illustrates a method for implementing location-based licensing, in accordance with another embodiment;

FIG. 3 illustrates a block diagram of an example of an environment wherein an on-demand database system might be used; and

FIG. 4 illustrates a block diagram of an embodiment of elements of FIG. 3 and various possible interconnections between these elements.

DETAILED DESCRIPTION General Overview

Systems and methods are provided for managing access to data based on information associated with a physical location of a user.

As used herein, the term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers.

Next, mechanisms and methods for managing access to data based on information associated with a physical location of a user will be described with reference to example embodiments.

FIG. 1 illustrates a method 100 for managing access to systems, products, and data based on information associated with a physical location of a user, in accordance with one embodiment. As shown in operation 102, information associated with a physical location of a user is identified. In one embodiment, the information may include current location information indicating the current physical location of the user. For example, the information may include location information indicating an exact physical location of the user, an approximate physical location of the user (e.g., a physical location accurate to within a predetermined threshold), etc.

Additionally, in one embodiment, the information may include coordinate information. For example, the information may include one or more geographical coordinates indicating the physical location of the user. In another embodiment, the information may be associated with a time. For example, the information may be associated with a time stamp that indicates a current time when the physical location of the user was determined.

Further, in one embodiment, the information may include an indication as to whether the user is within a predetermined range of a predetermined location. For example, the information may include an indication as to whether the user is within a predetermined distance from the predetermined location. In another embodiment, the information may include an indication as to whether the user is inside or within a predetermined distance from a predetermined building, vehicle, landmark, other user (e.g., a supervising manager), etc.

Further still, in one embodiment, the information associated with the physical location of the user may be identified utilizing one or more protocols. For example, the information may be identified utilizing a global positioning system (GPS) module and a GPS protocol. In another example, the information may be identified utilizing a Bluetooth (or low-energy Bluetooth) module and a Bluetooth (or low-energy Bluetooth) protocol. In yet another example, the information may be identified utilizing a radio frequency identification (RFID) module and an RFID protocol. In still another example, the information may be identified utilizing a nearfield communication module and a nearfield communication protocol. Of course, however, the information may be identified utilizing any module or modules and any protocol or protocols.

Also, in one embodiment, the information associated with the physical location of the user may be identified utilizing one or more devices. For example, the information may be identified utilizing a location aware device such as a smart phone, tablet, desktop, or other portable or non-portable computing device. In another embodiment, the information associated with the physical location of the user may be identified when it is received from another device. For example, a first device may calculate the physical location of the user and may send such calculated location to a second device. In yet another device, the physical location of the user may be identified by a multi-tenant, on-demand database system.

Additionally, it should be noted that, as described above, such multi-tenant on-demand database system may include any service that relies on a database system that is accessible over a network, in which various elements of hardware and software of the database system may be shared by one or more customers (e.g. tenants). For instance, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. Various examples of such a multi-tenant on-demand database system will be set forth in the context of different embodiments that will be described during reference to subsequent figures.

Further still, as shown in operation 104, access to one or more of systems, products, and data is managed, based on the identified information. In one embodiment, the data may include data stored within a system. For example, the data may include data stored within a multi-tenant, on-demand database system. In another embodiment, the data may include one or more applications or services. In yet another embodiment, the data may include confidential data, text data, image data, audio data, video data, etc. In another embodiment, the one or more systems may include one or more database systems, service provider systems, information systems, or any other systems able to be accessed by one or more users. In yet another embodiment, the one or more products may include one or more applications, one or more devices, one or more services, etc.

In yet another embodiment, managing access to data may include conditionally enabling one or more portions of a license that controls the access to the data. For example, the license may include an agreement (e.g. a legal instrument, etc.) that regulates the use or distribution of the data, and one or more portions of the license may be activated, based on the information. In still another embodiment, the license may be provided by the system that stores the data (e.g., the multi-tenant, on-demand database system, etc.). Further still, the managed access may control which user can utilize specific business functions or processing logic based on that users location.

Also, in one embodiment, managing the access to data may include determining whether one or more licenses are currently available to the user, based on the identified information. For example, the information associated with the physical location of the user at a current time period may be compared against one or more predetermined criteria to determine whether one or more licenses are available to the user at the current time period. In another example, one or more licenses may be associated with a predetermined location, and such licenses may be retrieved when it is determined that the user is currently at (or within a predetermined distance from) the predetermined location.

For example, if the information associated with the physical location of the user indicates that the user is currently located at a first location, a first license allowing access to a first set of data may be retrieved and provided to the user. In another example, if the information associated with the physical location of the user indicates that the user is currently located at a second location different from the first location, a second license different from the first license may be provided to the user, where the second license allows access to a second set of data different from the first set of data.

In addition, in one embodiment, additional information may be analyzed in conjunction with the identified information in order to determine whether one or more licenses are available to the user. For example, one or more of a user identifier (ID), a password, a security key, and other information may be provided by the user and may be analyzed in addition to the information associated with the physical location of the user in order to determine whether one or more licenses are currently available to the user.

Further, managing the access to data may include allowing access to one or more portions of data according to one or more licenses if it is determined that the physical location of the user matches (or is within a predetermined distance from) one or more predetermined locations. For example, a license allowing the access of one or more databases, tables, objects, processing capability, computing resources, etc. may be activated when it is determined that the user is physically located within a predetermined area.

Further still, in one embodiment, managing the access to data may include disallowing access to one or more portions of the data if it is determined that the physical location of the user does not match (or is not within a predetermined distance from) one or more predetermined locations. For example, the license allowing the access of one or more databases, tables, objects, etc. may be deactivated when it is determined that the user is not physically located within a predetermined area.

Also, in one embodiment, managing access to the data may include conditionally providing the user with login information necessary to access predetermined data, based on the information associated with the physical location of the user. For example, if it is determined that the user is physically located within a predetermined area associated with a license, system login information (e.g., one or more of a user name, name, password, key, etc.) associated with that license may be provided to the user for logging in to a system to access predetermined data in accordance with the license. In another example, if it is determined that the user is not physically located within a predetermined area, system login information associated with the license may be withheld from the user.

FIG. 2 illustrates a method 200 for implementing location-based licensing, in accordance with another embodiment. As an option, the method 200 may be carried out in the context of the functionality of FIG. 1. Of course, however, the method 200 may be carried out in any desired environment. The aforementioned definitions may apply during the present description.

As shown in operation 202, a location of a user is identified. In one embodiment, the location of a user may include a physical location of the user. In another embodiment, the location of the user may be identified for a particular time period (e.g., a current time period, etc.). In yet another embodiment, the location of the user may be determined by a device associated with the user. For example, the location of the user may be determined by a portable device carried by or located on the user (e.g., a portable computing device such as a cellular telephone, a communication device such as an RFID tag, etc.).

Additionally, in one embodiment, the location of the user may be identified using a near field communication (NFC) device, a GPS device, etc. In another embodiment, additional information associated with the user may be identified. For example, an identifier of the user (e.g., one or more of a user name, password, fingerprint, retina scan, facial image, etc.) may be obtained in addition to the location of the user. In another example, a time associated with the location identification (e.g., a time at which the location of the user was identified) may also be determined.

Further, as shown in operation 204, an availability of one or more licenses is determined, based at least in part on the identified location of the user. In one embodiment, the availability may be determined at a server. For example, determining the availability of one or more licenses may include sending the identified location of the user (along with any additional information that was identified) to a server of a system (e.g., a multi-tenant, on-demand database system, etc.). In another embodiment, determining the availability of one or more licenses may include comparing the sent information to a license database (e.g., a database containing a plurality of licenses controlling data access within the system) at the server (e.g., utilizing one or more applications of the server, etc.) and determining whether the sent information matches any available licenses.

In another embodiment, determining the availability of one or more licenses may include comparing the sent information to one or more additional criteria (e.g., one or more predetermined criteria such as an acceptable predetermined location, acceptable distance from a predetermined location, acceptable identification and password information, acceptable current time, etc.) to determine if the sent information meets the one or more criteria. In yet another embodiment, one or more licenses may be determined to be available if the sent information meets the one or more criteria. In another embodiment, no licenses may be determined to be available if the sent information does not meet the one or more criteria.

Further still, in one embodiment, the availability may be determined at a client. For example, determining the availability of one or more licenses may include comparing the identified location of the user (along with any additional information that was identified) to a license database (e.g., a database containing a plurality of licenses controlling data access within the system) at the client (e.g., using one or more applications of the client, etc.) and determining whether the identified information/location matches any available licenses. In another embodiment, if a match is determined at the client, an indication of such a match (which may include an indication of the matching licenses) may be sent to a server from the client.

Also, in one embodiment, if it is determined that multiple licenses are available to the user, the user may be presented with the multiple licenses (e.g., using an interface, etc.) and may select one or more of the available licenses to be used to provide access to data. In another embodiment, all licenses determined to be available to the user may be used to provide the user with access to data.

In addition, as shown in operation 206, access to data is conditionally provided to the user, based on the determined availability. In one embodiment, if it is determined that one or more licenses are available, data access may be provided to the user in accordance with the one or more licenses. For example, an application of a user device may be able to retrieve, send, and/or store data to/from one or more databases of the system, according to the one or more licenses. In another example, one or more applications of the system may be accessed by the user, according to the one or more licenses. In another embodiment, if it is determined that one or more licenses are not available, data access may not be provided to the user.

Furthermore, in one embodiment, a charge associated with data licensing may be reduced in response to implementing location-based licensing. For example, a data and/or service provider may charge a predetermined amount for an unrestricted license to access a provided service and/or data, and may charge a reduced amount (e.g., an amount less than the predetermined amount, etc.) for a license to access a provided service and/or data where such access is restricted to a particular physical location of the user.

Further still, in one embodiment, a charge associated with a first license may be applied to data access when a user is at a first predetermined location (or within a predetermined distance from the first predetermined location), and a second charge (e.g., larger than the first charge) may be applied to data access when the user is at a second location other than the first predetermined location (or is not within a predetermined distance from the first predetermined location).

In another embodiment, a central cloud-based application may verify the availability of one or more licenses based on the user and the location of the user. In another embodiment, if a license is available, an application of the user may be allowed to connect to a server of the system, according to the license.

Also, in one embodiment, the access to data may include access to medical data. For example, members of fitness or medical clinics may want to track information related to their weight, blood pressure, etc. In another example, when a user attempts to access fitness or medical data from a mobile device, a location of the user may be submitted to a server in addition to their identification and password information. This location information may be compared to one or more criteria to determine whether a license to access fitness or medical data is available. For example, the criteria may indicate that the location of the user must be at a fitness or medical clinic at a time when the fitness or medical clinic is open (e.g., business operating hours) to obtain a license to access the fitness or medical data. In this way, the number of license-based connections may be restricted to those users who have a business case for connecting. This may reduce concurrent usage and license costs.

Additionally, in one embodiment, a non-profit organization that uses volunteers to accept donations at a drop-off location may use the technology disclosed to monitor donations that are made. This may ensure that there are no faulty products or spoiled food, which may require a full audit trail including a photo and the receiver's signature. The technology disclosed may use proximity devices to license various drop-off locations based on the proximity model and may allow the non-profit organizations to provide volunteering based licensing.

Further, in one embodiment, the technology disclosed can use business drivers for licensing products based on location. For example, a franchise with multiple store managers and assistant managers may use the technology disclosed to implement a licensing model that limits access to store location for a single manager and five other employees.

Further still, in one embodiment, the technology disclosed can use near field communication to determine and provide the keys used during a login process. In another embodiment, it GPS coordinates may be provided to verify a site location. In yet another embodiment, cellular triangulation or Wi-Fi acquired signatures may be used to verify a current location of a user.

Also, in one embodiment, a user may request classified information, where access to such information is controlled by a license. For example, a current location of the user may be sent along with an identification of the user and the request for the classified information. Such current location may be compared against criteria indicating acceptable locations to view such classified information, and the identification of the user may be compared against licenses issued to that user to view classified information. In another example, if a license exists that matches the current location of the user and the identification of the user, the license may be activated and the user may view all or some of the requested classified information according to that license. In yet another example, if no license exists that matches the current location of the user and the identification of the user, the user may not view the requested classified information.

Additionally, in one embodiment, a user may visit a predetermined location (e.g., a doctor's office, a dentist's office, etc.). Further, the user's location may be identified by a device of the user and may be sent to a server. Further still, the user's location may be compared against one or more criteria to determine whether one or more licenses are available to users at that location. For example, an entity associated with the predetermined location may purchase a license to access content (e.g., magazine data, video data, etc.), where such license may be available to all users located at the predetermined location within a predetermined time period (e.g., within the business hours of the office, etc.). Also, if it is determined that a license is available to users at the location, the license may be temporarily assigned to the user (e.g., to the device of the user), such that the user may access content in accordance with the license while the user is physically located at the predetermined location. Additionally, in on embodiment, the user's access may be related to their relative location to a secondary device or user. For example, access to personal records may be prevented if the user is trying to connect to a device while their location aware cell phone is not within the immediate vicinity of a predetermined location, and employee's access to view confidential information may be allowed while a manager's cell phone is within the immediate vicinity of the employees.

System Overview

FIG. 3 illustrates a block diagram of an environment 310 wherein an on-demand database system might be used. Environment 310 may include user systems 312, network 314, system 316, processor system 317, application platform 318, network interface 320, tenant data storage 322, system data storage 324, program code 326, and process space 328. In other embodiments, environment 310 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.

Environment 310 is an environment in which an on-demand database system exists. User system 312 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 312 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in FIG. 3 (and in more detail in FIG. 4) user systems 312 might interact via a network 314 with an on-demand database system, which is system 316.

An on-demand database system, such as system 316, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database systems may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database system 316” and “system 316” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 318 may be a framework that allows the applications of system 316 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database system 316 may include an application platform 318 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database system, users accessing the on-demand database system via user systems 312, or third party application developers accessing the on-demand database system via user systems 312.

The users of user systems 312 may differ in their respective capacities, and the capacity of a particular user system 312 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 312 to interact with system 316, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 316, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.

Network 314 is any network or combination of networks of devices that communicate with one another. For example, network 314 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that the one or more implementations might use are not so limited, although TCP/IP is a frequently implemented protocol.

User systems 312 might communicate with system 316 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 312 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 316. Such an HTTP server might be implemented as the sole network interface between system 316 and network 314, but other techniques might be used as well or instead. In some implementations, the interface between system 316 and network 314 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.

In one embodiment, system 316, shown in FIG. 3, implements a web-based customer relationship management (CRM) system. For example, in one embodiment, system 316 includes application servers configured to implement and execute CRM software applications as well as provide related data, code, forms, webpages and other information to and from user systems 312 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, system 316 implements applications other than, or in addition to, a CRM application. For example, system 316 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 318, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 316.

One arrangement for elements of system 316 is shown in FIG. 3, including a network interface 320, application platform 318, tenant data storage 322 for tenant data 323, system data storage 324 for system data 325 accessible to system 316 and possibly multiple tenants, program code 326 for implementing various functions of system 316, and a process space 328 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 316 include database indexing processes.

Several elements in the system shown in FIG. 3 include conventional, well-known elements that are explained only briefly here. For example, each user system 312 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. User system 312 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 312 to access, process and view information, pages and applications available to it from system 316 over network 314. Each user system 312 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 316 or other systems or servers. For example, the user interface device can be used to access data and applications hosted by system 316, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 312 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 316 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 317, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring system 316 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 316 is configured to provide webpages, forms, applications, data and media content to user (client) systems 312 to support the access by user systems 312 as tenants of system 316. As such, system 316 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.

FIG. 4 also illustrates environment 310. However, in FIG. 4 elements of system 316 and various interconnections in an embodiment are further illustrated. FIG. 4 shows that user system 312 may include processor system 312A, memory system 312B, input system 312C, and output system 312D. FIG. 4 shows network 314 and system 316. FIG. 4 also shows that system 316 may include tenant data storage 322, tenant data 323, system data storage 324, system data 325, User Interface (UI) 430, Application Program Interface (API) 432, PL/SOQL 434, save routines 436, application setup mechanism 438, applications servers 400 ₁-400 _(N), system process space 402, tenant process spaces 404, tenant management process space 410, tenant storage area 412, user storage 414, and application metadata 416. In other embodiments, environment 310 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.

User system 312, network 314, system 316, tenant data storage 322, and system data storage 324 were discussed above in FIG. 3. Regarding user system 312, processor system 312A may be any combination of one or more processors. Memory system 312B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 312C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 312D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 4, system 316 may include a network interface 320 (of FIG. 3) implemented as a set of HTTP application servers 400, an application platform 318, tenant data storage 322, and system data storage 324. Also shown is system process space 402, including individual tenant process spaces 404 and a tenant management process space 410. Each application server 400 may be configured to tenant data storage 322 and the tenant data 323 therein, and system data storage 324 and the system data 325 therein to serve requests of user systems 312. The tenant data 323 might be divided into individual tenant storage areas 412, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage area 412, user storage 414 and application metadata 416 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 414. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area 412. A UI 430 provides a user interface and an API 432 provides an application programmer interface to system 316 resident processes to users and/or developers at user systems 312. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.

Application platform 318 includes an application setup mechanism 438 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 322 by save routines 436 for execution by subscribers as one or more tenant process spaces 404 managed by tenant management process 410 for example. Invocations to such applications may be coded using PL/SOQL 434 that provides a programming language style interface extension to API 432. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned co-pending U.S. Provisional Patent Application 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEM FOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, by Craig Weissman, filed Oct. 4, 2006, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manages retrieving application metadata 416 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.

Each application server 400 may be communicably coupled to database systems, e.g., having access to system data 325 and tenant data 323, via a different network connection. For example, one application server 400 ₁ might be coupled via the network 314 (e.g., the Internet), another application server_(N-1) might be coupled via a direct network link, and another application server 400 _(N) might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 400 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 400 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 400. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 400 and the user systems 312 to distribute requests to the application servers 400. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 400. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 400, and three requests from different users could hit the same application server 400. In this manner, system 316 is multi-tenant, wherein system 316 handles storage of, and access to, different objects, data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 316 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 322). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 316 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data, system 316 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.

In certain embodiments, user systems 312 (which may be client systems) communicate with application servers 400 to request and update system-level and tenant-level data from system 316 that may require sending one or more queries to tenant data storage 322 and/or system data storage 324. System 316 (e.g., an application server 400 in system 316) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 324 may generate query plans to access the requested data from the database.

Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain embodiments, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.

While one or more implementations have been described by way of example and in terms of the specific embodiments, it is to be understood that one or more implementations are not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. 

1-20. (canceled)
 21. A method, comprising: accessing, by a computer system, permission information for a data store, wherein the permission information indicates, for a particular user, a plurality of permissions, each of which permits the particular user to access a particular portion of the data store while the particular user is located within a respective specified geographical region; receiving, from the particular user by the computer system, a request to access data; receiving, by the computer system, location information indicating a current geographical location of the particular user; and in response to the request, the computer system determining whether to permit access to the data store based on the location information and the plurality of permissions for the particular user.
 22. The method of claim 21, wherein the determining includes denying access to the data store based on the location information indicating that the particular user is not within one of the respective geographical regions specified by the plurality of permissions for the particular user.
 23. The method of claim 21, wherein the plurality of permissions include a particular permission that permits the particular user to access the corresponding particular portion of the data store during a particular time frame.
 24. The method of claim 23, further comprising: receiving, from the particular user by the computer system, another request to access data; receiving, by the computer system, additional location information that indicates a second geographical location of the particular user and a time at which the second geographical location of the particular user was determined; and in response to the other request, the computer system preventing, based on the time not being within the particular time frame, the particular user from accessing the particular portion of the data store that corresponds to the particular permission.
 25. The method of claim 21, wherein the plurality of permissions include a particular permission that indicates that the particular user's access to the corresponding particular portion of the data store is permitted based on whether the particular user is included in a set of users permitted to access the corresponding particular portion of the data store.
 26. The method of claim 21, wherein the plurality of permissions includes a first permission indicating a first level of access to the data store when the particular user is within a first geographical region, and wherein the plurality of permissions includes a second permission indicating a second, different level of access to the data store when the particular user is within a second, different geographical region.
 27. The method of claim 26, wherein the first geographical region is within the physical premises of an entity, and wherein the second geographical region is a location remote to the physical premises of the entity.
 28. The method of claim 21, wherein the respective specified geographical region specified for a particular one of the plurality of permissions corresponds to a set of buildings.
 29. A non-transitory computer readable medium having program instructions stored thereon that are capable of causing a computer system to perform operations comprising: determining that a user is physically located within a first region; enabling the user to access a first set of data in accordance with a first permission that permits the user to access the first set of data only while the user is physically located within the first region; determining that the user is physically located within a second region; and enabling the user to access a second set of data in accordance with a second permission that permits the user to access the second set of data only while the user is physical located within the second region, wherein the second set of data is different than the first set of data.
 30. The medium of claim 29, wherein the first and second regions correspond to distinct regions, and wherein the operations further comprise: in response to determining that the user is physically located within the second region, preventing the user from accessing the first set of data.
 31. The medium of claim 29, wherein the operations further comprise: determining a current time that is associated with the computer system, wherein enabling the user to access the second set of data is further based on whether the current time is within a time frame during which access to the second set of data is permitted.
 32. The medium of claim 29, wherein the operations further comprise: determining that the user is physically located at a third region; and based on the third region not being within the first and second regions, preventing the user from accessing the first and second sets of data.
 33. The medium of claim 29, wherein the operations further comprise: receiving, from a computer system of the user, global positioning system information that indicates a physical location of the user; and determining where the user is physically located based on the received global positioning system information.
 34. The medium of claim 29, wherein enabling the user to access the second set of data includes: sending, to a computer system of the user, login information usable by the user to access the second set of data while the user is physically located within the second region.
 35. The medium of claim 29, wherein the operations further comprise: receiving, from a computer system of the user, login information associated with the user, wherein enabling the user to access the second set of data is based on the login information being authentic.
 36. A method, comprising: receiving, from a user device of a user by a computer system, a request to access data; receiving, by the computer system, first location information that indicates a first location of the user; based on the first location of the user, the computer system determining a permission from a set of permissions that permits the user to access a respective set of data while the user is within a respective region, wherein the set of permissions includes: a first permission that permits the user to access a first set of data only while the user is physically located within a first region; and a second permission that permits the user to access a second, different set of data only while the user is physically located within a second region; and enabling, by the computer system, the user to access the respective set of data in accordance with the determined permission while the user is within the respective region indicated by the determined permission.
 37. The method of claim 36, further comprising: receiving, by the computer system, second location information that indicates a second location of the user; and in response to the second location not being within the respective region indicated by the determined permission, the computer system preventing the user from accessing the respective set of data.
 38. The method of claim 37, further comprising: based on the second location of the user, the computer system determining whether the set of permissions includes a permission associated with the second location; and based on determining that the set of permissions does not include a permission associated with the second location, the computer system preventing the user from accessing data associated with the set of permissions.
 39. The method of claim 36, wherein the first location information indicates a time at which the first location of the user was determined, and wherein determining the permission from the set of permissions is further based on the time indicated by the first location information.
 40. The method of claim 36, wherein the determined permission indicates operations that the user can request the computer system to perform on the respective set of data. 